☁️ Nx Cloud Report

CI ran the following commands for commit 7b03831. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Sent with 💌 from NxCloud.

ohhhhhh, I see, the . is in yarn lint, not within yarn lint:js. That's confusing, since I was expecting to be able to run just the subcommand without needing to supply extra arguments.

Note, this does mean that it's a bit trickier to run linting on a specific file or folder. However, that's a bit of an anti-pattern anyway when caching is enabled, because it will remove your cache file if you do not lint the same thing each time. So, it's usually faster to just run the lint-everything command, than to change what you're linting and keep blowing away the cache. So, I stand behind this change, but wanted to explain the reasoning in case anyone is used to running yarn lint:js path/to/my/file.ts.

If anyone does want to run against a single file (maybe because there are too many warnings in other files?), it's still possible with yarn cross-env NODE_ENV=production eslint --cache --cache-location=.cache/eslint --ext .js,.jsx,.json,.html,.ts,.tsx,.mjs --report-unused-disable-directives path/to/my/file.ts. I'd be happy to discuss other alternatives as well, like adding a separate script, if this is a common workflow.